- 
          
- 
                Notifications
    You must be signed in to change notification settings 
- Fork 33.3k
          gh-125842: Fix sys.exit(0xffff_ffff) on Windows
          #125896
        
          New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
          
     Merged
      
      
    
                
     Merged
            
            
          Conversation
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
    On Windows, `long` is a signed 32-bit integer so it can't represent 0xffff_ffff without overflow. Windows exit codes are unsigned 32-bit integers, so if a child process exits with `-1`, it will be represented as 0xffff_ffff. Also fix a number of other possible cases where `_Py_HandleSystemExit` could return with an exception set, leading to a `SystemError` (or fatal error in debug builds) later on during shutdown.
              
                    nineteendo
  
              
              reviewed
              
                  
                    Oct 23, 2024 
                  
              
              
            
            
Co-authored-by: Nice Zombies <[email protected]>
| 🤖 New build scheduled with the buildbot fleet by @colesbury for commit 8864fef 🤖 If you want to schedule another build, you need to add the 🔨 test-with-buildbots label again. | 
              
                    picnixz
  
              
              reviewed
              
                  
                    Oct 23, 2024 
                  
              
              
            
            
Co-authored-by: Bénédikt Tran <[email protected]>
              
                    Yhg1s
  
              
              approved these changes
              
                  
                    Oct 24, 2024 
                  
              
              
            
            
| Thanks @colesbury for the PR 🌮🎉.. I'm working now to backport this PR to: 3.13. | 
    
  miss-islington 
      pushed a commit
        to miss-islington/cpython
      that referenced
      this pull request
    
      Oct 24, 2024 
    
    
      
  
    
      
    
  
) On Windows, `long` is a signed 32-bit integer so it can't represent `0xffff_ffff` without overflow. Windows exit codes are unsigned 32-bit integers, so if a child process exits with `-1`, it will be represented as `0xffff_ffff`. Also fix a number of other possible cases where `_Py_HandleSystemExit` could return with an exception set, leading to a `SystemError` (or fatal error in debug builds) later on during shutdown. (cherry picked from commit ad6110a) Co-authored-by: Sam Gross <[email protected]>
| GH-125925 is a backport of this pull request to the 3.13 branch. | 
    
  colesbury 
      added a commit
      that referenced
      this pull request
    
      Oct 24, 2024 
    
    
      
  
    
      
    
  
…H-125925) On Windows, `long` is a signed 32-bit integer so it can't represent `0xffff_ffff` without overflow. Windows exit codes are unsigned 32-bit integers, so if a child process exits with `-1`, it will be represented as `0xffff_ffff`. Also fix a number of other possible cases where `_Py_HandleSystemExit` could return with an exception set, leading to a `SystemError` (or fatal error in debug builds) later on during shutdown. (cherry picked from commit ad6110a) Co-authored-by: Sam Gross <[email protected]>
    
  ebonnal 
      pushed a commit
        to ebonnal/cpython
      that referenced
      this pull request
    
      Jan 12, 2025 
    
    
      
  
    
      
    
  
On Windows, `long` is a signed 32-bit integer so it can't represent `0xffff_ffff` without overflow. Windows exit codes are unsigned 32-bit integers, so if a child process exits with `-1`, it will be represented as `0xffff_ffff`. Also fix a number of other possible cases where `_Py_HandleSystemExit` could return with an exception set, leading to a `SystemError` (or fatal error in debug builds) later on during shutdown.
  
    Sign up for free
    to join this conversation on GitHub.
    Already have an account?
    Sign in to comment
  
      
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
On Windows,
longis a signed 32-bit integer so it can't represent0xffff_ffffwithout overflow. Windows exit codes are unsigned 32-bit integers, so if a child process exits with-1, it will be represented as0xffff_ffff.Also fix a number of other possible cases where
_Py_HandleSystemExitcould return with an exception set, leading to aSystemError(or fatal error in debug builds) later on during shutdown.